Method and Node For Measuring Processing Power in a Node in a Communications Network

ABSTRACT

The embodiments herein relate to a method in a first network node ( 105 ) for measuring processing power in a second network node ( 103 ) in a communications network ( 100 ). The first network node ( 105 ) obtains a signaling load value associated with a procedure, which procedure is triggered by a message. Based on the obtained signaling load value, the first network node ( 105 ) measures the processing power of the second network node ( 103 ).

TECHNICAL FIELD

Embodiments herein relate generally to a first network node and a methodin the first network node. More particularly the embodiments hereinrelate to measuring processing power in a second network node in thecommunications network.

BACKGROUND

A typical communications network or system is a collection of UserEquipments (UE), links and network nodes which together enablecommunication between the user equipments. In the communicationsnetwork, which also may be referred to as cellular network, the userequipments, communicate via a Radio Access Network (RAN) to one or morecore networks (CN).

A user equipment is a mobile terminal by which a subscriber may accessservices offered by an operator's core network and services outside theoperator's network to which the operator's RAN and CN provide access.User equipments are enabled to communicate wirelessly in the cellularnetwork. The user equipments may be for example communication devicessuch as mobile telephones, cellular telephones, laptops with wirelesscapability, machine-to-machine devices, or embedded devices in otherelectronic equipment. The user equipments may be portable,pocket-storable, hand-held, computer-comprised, or vehicle-mountedmobile devices, enabled to communicate voice and/or data, via the radioaccess network, with another entity, such as another user equipment or aserver.

The communications network covers a geographical area which is dividedinto cell areas. Each cell area is served by a base station, e.g. aRadio Base Station (RBS), which sometimes may be referred to as e.g.evolved Node B (eNB), eNodeB, NodeB, B node, or Base Transceiver Station(BTS), depending on the technology and terminology used. A cell is ageographical area where radio coverage is provided by the base stationat a base station site. Each cell is identified by an identity withinthe local radio area, which is broadcast in the cell. The base stationscommunicate over the air interface operating on radio frequencies withthe user equipments within range of the base stations

In some versions of the radio access network, several base stations aretypically connected, e.g. by landlines or microwave, to a Radio NetworkController (RNC), as in 3^(rd) Generation (3G), i.e. Wideband CodeDivision Multiple Access (WCDMA). The radio network controllersupervises and coordinates various activities of the plural basestations connected thereto. In 2^(nd) Generation (2G), i.e. GlobalSystem for Mobile Communications (GSM), the base stations are connectedto a Base Station Controller (BSC). The network controllers aretypically connected to one or more core networks.

Machine-to-Machine (M2M) is a term referring to technologies that allowboth wireless and wired systems to communicate with other devices of thesame ability, for example computers, embedded processors, smart sensors,actuators and mobile devices may communicate with one another, takemeasurements and make decisions, often without human intervention.Machine Type Communication (MTC) may be seen as a form of datacommunication between entities that do not necessarily need humaninteraction. M2M traffic is, for example, used in applications such aselectricity meters, home alarms, signaling from vehicles, such as e.g.cars, trucks etc.

There exists a clear industry consensus that mobile machine-to-machinecommunications will play an increasingly prominent role in carriernetworks and Information Technology (IT) operations. It may be predictedthat there will be 50 billion wirelessly connected devices by the yearof 2020. These devices may be connected via GSM, High Speed PacketAccess (HSPA) and Long Term Evolution (LTE), and will be used for bothmachine-to-machine applications and connected consumer devices.

It is commonly believed that M2M communication will be applied in a longrange of very different areas with completely different communicationrequirements and patterns. Some electricity meter applications may forexample connect and communicate just a few bytes of data only once amonth, whereas other applications such as video surveillance may beconstantly connected and transfer Gigabyte of data every hour.Connecting M2M devices with such different communication patterns to thesame infrastructure as is used for normal human-to-human (H2H)communication puts new challenges on the communication equipment. New3rd Generation Partnership Project (3GPP) requirements related to M2Mcommunication have been specified to try to address some of thesechallenges. A service optimized for machine type communications isdifferent from a service optimized for H2H communications. Machine typecommunications is different from current mobile network communicationservices as it may involve:

-   -   different market scenarios,    -   data communications,    -   lower costs and effort,    -   a potentially very large number of communicating user equipments        with,    -   for many applications, little traffic per user equipment.

M2M devices, also referred to as MTC devices, that do not move, moveinfrequently, or move only within a certain region may be associatedwith a feature called “low mobility”. A requirement for low mobility maybe that the network operator may be able to change the frequency ofmobility management procedures or simplify mobility management per M2Mdevice. Another requirement may be that the network operator may be ableto define the frequency of location updates performed by the M2M device.M2M devices that are expected to send or receive data infrequently, i.e.with long period between two data transmission, may be associated with afeature called infrequent transmission. For the infrequent transmission,the network shall establish a resource only when transmission occurs.

One serious problem with connecting M2M devices with new communicationpatterns to the same infrastructure as is used for H2H communication ishow the model for dimensioning of network nodes are currently designed.The state-of-the-art is that the dimension of a communication node isoften based on the number of served user equipments and/or the numberconnections the node may handle. Another problem relating to connectingM2M devices with new communication patterns to the same infrastructureas is used for H2H communication is how the price model and licensing ofnetwork nodes are currently designed. The price of a communication nodeis may also be based on the number of served user equipments and/or thenumber connections the node may handle. This is also naturally relatedto the Average Revenue Per User (ARPU) which is an important measure foroperators.

When looking closer at what resources user equipments and connectionsconsume in the network, it is found that they consume two types ofresources, memory resources and processing resources. The networkequipment may also be referred to as a communication node or networknode. Memory resources in the network node are used to store certainparameters related to a user equipment that is registered in the node,i.e. the network, or related to a connection that is established in thenode, i.e. in the network. Processing resources are needed when thestate of user equipments or connections are changed, e.g. registering auser equipment in the network/node or deregistering a user equipment,establishing a new connection or removing it, changing the state of aconnection from idle to connected, or vice versa, or changing thecurrent location of a registered user equipment etc. Processingresources are also needed for some other purposes, e.g. regularlychecking the reachability of a user equipment/terminal, or notifying theuser equipment or network of certain events such as that someone wantsto communicate with it.

When dimensioning the hardware for a communication/network node, ingeneral the amount of required memory resources and processing resourcesneed to be decided. This is usually done by trying to define a “typicaluser equipment”. This is accomplished by a “traffic model”, whichdefines e.g. how many registrations/deregistrations a typical userequipment does per day, how many times per hour it initiatescommunication, how much the typical user equipment moves betweendifferent cells and mobility areas etc. Through the traffic model, thebalance between memory and processing resources will be known, and hencethe hardware may be properly dimensioned. When the hardware isdimensioned the price may be set based on the number of user equipmentsand/or connections that the node may serve. When a traffic model is usedas a base for node dimensioning and pricing/licensing, there will be acertain balanced relation between memory and processing resources.

A problem with connecting M2M devices to the same infrastructure as H2Huser equipments is that there is no “typical user equipment” for M2M.They are expected to span over a wide range of different communicationbehaviors. Optimization for M2M that is being done in 3GPP has made thisspan even larger. Therefore it becomes very difficult to use “trafficmodels” as a base for hardware dimensioning and therefore also forprice/license models. A more flexible approach for dimensioning ofnetwork nodes is therefore required.

Some M2M areas, often with “low activity” communication patterns, arealso expected to be cost sensitive. It is therefore important that theprice/license models are flexible enough, so that they don't prohibitsuch M2M communication to use the 3GPP infrastructures.

The growing use of Smart Phones has to some extent also put requirementson changed or more flexible traffic models, but with the expected growthof M2M devices the problem is growing critical.

In addition to memory and processing resources, the hardware of acommunication node that handles payload, i.e. forwards IP packets, isalso dimensioned based on its packet forwarding capacity measured inPackets Per Second (PPS), or simply its throughput capacity measured inGiga- or Terabit per second. In some embodiments, a communication nodemay also be priced based on its packet forwarding capacity measured inPackets Per Second (PPS), or simply its throughput capacity measured inGiga- or Terabit per second. However, since the hardware for payloadhandling is normally quite separate from the hardware resourcesdescribed above, it may to a certain extent be dimensioned and pricedseparately.

SUMMARY

An objective of embodiments herein is therefore to obviate at least oneof the above disadvantages and to provide flexible dimensioning of anetwork node.

According to a first aspect, the objective is achieved by a method in afirst network node for measuring processing power in a second networknode in a communications network. The first network node obtains asignaling load value associated with a procedure. The procedure istriggered by a message. The first network node measures the processingpower of the second network node based on the obtained signaling loadvalue.

According to a second aspect, the objective is achieved by a firstnetwork node for measuring processing power in a second network node ina communications network. The first network node comprises an obtainingunit configured to obtain a signaling load value associated with aprocedure. The procedure is triggered by a message. The second networknode further comprises a measuring unit configured to measure theprocessing power of the second network node in the communicationsnetwork based on the obtained signaling load value.

Thanks to the signalling load value, which is tied to the processingresource utilization in the second network node, and flexibledimensioning of the second network node is achieved, in addition to away to measure the resource utilization in the second network node.

Embodiments herein afford many advantages, of which a non-exhaustivelist of examples follows:

The embodiments herein provide an advantage of an easy and flexible wayof measuring the true processing power capacity of a complexcommunication node with a large number of very different processingtasks.

By decoupling memory resources and processing resources, dimensioningflexibility may be achieved. The dimensioning model may accommodatedifferent usage behaviors and usage patterns in a flexible way. It mayfor example be possible for low activity cost sensitive M2M applicationsto use 3GPP infrastructure as their communication means with arelatively smaller amount of processing power and infrastructure costfor the mobile operator. In some embodiments, this is also applicable toa price/license model of the second network node.

Another advantage is that the vendor is relieved from the responsibilityof maintaining an adequate node dimensioning that fits any used trafficmodel. Instead that responsibility is shifted to the user of the node,e.g. the operator, who monitors utilization of the two resourcesseparately and takes action, e.g. increases the network node capacity,when any one of the two resources reaches its capacity limit.

It is further an advantage that the vendor may more easily provideproducts or nodes that are dimensioned for different usages. For examplea network node dimensioned and tailored for “low activity” M2M devicesthat may hold ten times more registered users or connections would bepossible using the same dimensioning model, and also using the samepricing/licensing model. Since node dimensioning does not need to bebased on a traffic model, and since the user of the node ensures himselfthat processing and memory resources both and independently are keptbelow the capacity limit, the vendor can offer a different or a tailorednode configurations with fair pricing/licensing regardless of thenetwork node configuration.

Another advantage is that the embodiments herein are usefulness foraddressing the capacity problems related to smart phones.

The embodiments herein are not limited to the features and advantagesmentioned above. A person skilled in the art will recognize additionalfeatures and advantages upon reading the following detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments herein will now be further described in more detail inthe following detailed description by reference to the appended drawingsillustrating the embodiments and in which:

FIG. 1 is a schematic block diagram illustrating embodiments of acommunications network.

FIG. 2 is a combined schematic block diagram and flowchart depictingembodiments of a method.

FIG. 3 is a schematic block diagram illustrating embodiments of acommunications network.

FIG. 4 is a schematic block diagram illustrating embodiments of acommunications network.

FIG. 5 is a flow chart illustrating embodiments of a method.

FIG. 6 is a schematic block diagram illustrating embodiments of a firstnetwork node

The drawings are not necessarily to scale and the dimensions of certainfeatures may have been exaggerated for the sake of clarity. Emphasis isinstead placed upon illustrating the principle of the embodimentsherein.

DETAILED DESCRIPTION

FIG. 1 depicts a communications network 100 in which embodiments hereinmay be implemented. The communications network 100 may in someembodiments apply to one or more radio access technologies such as forexample LTE, LTE Advanced, WCDMA, GSM, or any other 3GPP radio accesstechnology. It may also apply to other existing or future radio accesstechnologies, e.g. Wireless Local Area Network (WLAN), Code DivisionMultiplexing Access (CDMA), or existing or future fixed accesstechnologies.

The wireless communications network 100 comprises a first network node105. The first network node 105 is a node which is normally integratedor embedded into another node. It may also be a stand alone node, butnormally, the first network node 105 is an internal node of anothernode. Examples of such nodes will be described later.

The wireless communications network 100 further comprises a secondnetwork node 103. The second network node 103 may be any suitable typeof network node capable of communicating with a fourth network node 101and the first network node 105. In some embodiments, the second networknode 103 is the node in which the first network node 105 is integratedor embedded, as illustrated as alternative 1 in FIG. 1.

The second network node 103 may be for example a Mobility ManagementEntity (MME), a Serving General Packet Radio Service Support Node,(SGSN), a Gateway General Packet Radio Service Support Node (GGSN), aServing Gateway, (S-GW), a Packet Data Network Gateway, (P-GW), aMachine Type Communication Interworking Function node (MTC IWF), a BaseTransceiver Station (BTS), a BSC, a NodeB, a RNC, an eNB and generallyin any network node that handles signaling and keeps a userequipment/connection related state. The fourth network node 101 whichcommunicates with the second network node 103 may be a user equipment orany network node, which communicate and sends control signaling to/fromthe second network node 103.

The user equipment 101 may be any suitable communication device orcomputational device with communication capabilities capable tocommunicate with a base station over a radio channel, for instance butnot limited to mobile phone, smart phone, Personal Digital Assistant(PDA), laptop, MP3 player or portable DVD player, or similar mediacontent devices, digital camera, electricity meters, home alarms, oreven stationary devices such as a Personal Computer (PC). A PC may alsobe connected via a mobile station as the end station of thebroadcasted/multicasted media. The user equipment 101 may also be anembedded communication device in e.g. electronic photo frames, cardiacsurveillance equipment, intrusion or other surveillance equipment,weather data monitoring systems, vehicle, car or transport communicationequipment, etc.

The communications network 100 may further comprise a third network node107, which may be a monitoring node such as for example an OperationSupport System (OSS) node or an Operations & Maintenance (O&M) node. Thethird network node 120 may be located in the mobile operator network orin another network e.g. at the node vendor. In some embodiments, thefirst network node 105 is integrated or embedded in the third networknode 107, as illustrated as alternative 2 in FIG. 1.

The embodiments herein handle memory resources and processing resourcesof the 20 second network node 103 separately. This may also be relevantwhen it comes to pricing and licensing. This will also mean that trafficmodels will be less important for the design and hardware composition ofnodes.

The existing measures, i.e. registered users, e.g. SimultaneouslyAttached Users (SAU), and the number of connections, i.e. Packet DataProtocol (PDP) contexts/Packet Data Network (PDN) connections, are keptbut tied more to the memory resource utilization in the second networknode 103.

The signaling and method steps illustrated in FIG. 1 will be describedin detail in relation to FIGS. 2 and 5 below.

The method for measuring processing power in the second network node 103in the communications network 100, according to some embodiments willnow be described with reference to the combined signaling diagram andflowchart depicted in FIG. 2 and with reference to FIG. 1, FIG. 3 andFIG. 4 depicting embodiments of the communications network 100.Alternative 1 of FIG. 1 is illustrated using a dotted square in FIG. 2,and alternative 2 of FIG. 1 is illustrated using a dotted circle in FIG.2. In the following, a user equipment 101 is used as an example for afourth network node 101. However, instead of a user equipment 101, thenode may be any fourth network node 101 configured to communicate withthe second network node 103. The second network node 103 may be forexample an MME, or any of the node as described above. The methodcomprises the following steps, which steps may as well be carried out inanother suitable order than described below.

Step 201

The user equipment 101 sends a message/signaling to the second networknode 103. The message may be referred to as an ingress message. In someembodiments, the message is an attach message, a detach message, aRouting Area Update Request message etc. Further examples of types ofmessages are exemplified in table 2 and table 3 below.

In some embodiments, a plurality of user equipments 101 sendsmessages/signaling to the second network node 103.

Step 202

The second network node 103 receives the message sent from the userequipment 101.

In some embodiments, when the first network node 103 is integrated orembedded into the third network node 107, the second network node 105creates a log comprising all messages received from the user equipment101. The log is an event log comprising historical data of received userequipment 101 messages. The log is stored in a computer readable memorycomprised in the second network node 105.

Step 203

The received message triggers execution of a procedure in the secondnetwork node 103. The execution of the procedure requires processingresources, or resources in general from it is initiated until it isfinalized in the second network node 103. This may comprise processingresources, bandwidth resources on different interfaces, primary andsecondary memory resources, and other physical or virtual resources suchas e.g. identifiers, encryption keys, security certificates, IPaddresses, etc., that may exist in limited amounts in the second networknode 103.

In some embodiments, a message may trigger different procedures. Forexample, message 1 may trigger procedure A or procedure B.

A procedure may be a series of operations or calculations which have tobe executed in the same manner in order to perform a task. A proceduremay be executed fully within one node, or parts of the procedure may beexecuted by other nodes. In the latter case the one node sends specificmessages to these other nodes and normally receives responses after sometime. In the following, a procedure relates to measurement in the onenode only without considering what happens in other nodes. However,measurements from different nodes may in some embodiments be aggregatedbefore presented.

Step 204 a

This step corresponds to alternative 1 in FIG. 1.

As mentioned above, in some embodiments, when the first network node 105is integrated or embedded in the second network node 103, the firstnetwork node 105 detects that the second network node 103 has received amessage from the user equipment 101.

Step 204 b

This corresponds to alternative 2 in FIG. 1, and is an alternative stepperformed instead of step 204 a.

In some embodiments, when the first network node 105 is integrated orembedded in the third network node 107, the second network node 103sends the stored information about the received message to the firstnetwork node 105. As mentioned above, the information about the receivedmessages are in the form of single message information or in the form ofmultiple messages in the event log stored in a computer readable memoryin the first network node 105.

Step 205

The first network node 105 obtains a signaling load value associatedwith the procedure triggered by the message.

The first network node 105 obtains the signaling load value from a tablewhich is stored in a computer readable memory in the first network node105. The table is used to translate all messages received at the secondnetwork node 103 that have any significant consumption of the processingpower/resource in the second network node 103, to an equivalent valuecalled Signaling Load Value (SLV). The signaling load value may also bereferred to as Signaling Load Unit (SLU) or signaling equivalent units,and it is tied to the processing power/resource utilization in thesecond network node 103. An example of a generic translation table isshown in table 1 below.

TABLE 1 Examples of translation of messages and procedures to normalizedSignaling Load Values for a second communication node 103 Parameter(s)or condition that Signaling Ingress distinguish Load Message procedureProcedure Value Message_1 Param X = nn Procedure A 1 Message_1 Param X =mm Procedure B 0.8 Message_2 — Procedure C 0.2 Message_3 — Procedure D1.5 Message_4 — Procedure E 0.1 Message_5 Condition Y is fulfilledProcedure F 0.7

The left most column comprises different messages received at the secondnetwork node 103. The messages may be ingress messages. An ingressmessage is an incoming message, while an egress message is an outgoingmessage. The middle right column comprises the procedures associatedwith and triggered by the received messages. Different messages andsignaling processed by the second network node 103 may be compared andsummarized based on the amount of processing power/resources theyconsume in the second network node 103 and hence forming a measure forthe signaling load value.

The value in the right most column of table 1, the signaling load value,have been set by the vendor of the second network node 103 or theoperator of the second network node 103, to correspond to how muchprocessing power/resources, or power/resources in general, the specificprocedure is estimated to consume in the second network node 103 from itis initiated until it is finalized. The signaling load value is aninstantaneous relative, i.e. normalized, value, i.e. the load generatedby a procedure initiated by a certain message, and optionally withspecific parameters or conditions, compared to one specific procedure,e.g. attach, that is used as a reference load. The load may be estimatedor measured. A factor may or may not be applied on each value. Inanother embodiment, procedures are compared not based on processingresources only, but to any second network node resources in general.This may comprise processing resources, bandwidth resources on differentinterfaces, primary and secondary memory resources, and other physicalor virtual resources such as e.g. identifiers, encryption keys, securitycertificates, IP addresses, etc., that may exist in limited amounts inthe second network node 103.

Note, in some cases the same message in the Ingress Message column maytrigger different procedures, e.g. see Procedure A & B above. Thenadditional information such as message parameters or some stateinformation in the second network node 103 is required to determinewhich “procedure” is executed and hence which signaling load value shallbe obtained. One “procedure” may in itself generate several messages ondifferent interfaces to and from other nodes before the procedure isconsidered finalized, but only the initiating message increases thetotal signaling load value. The middle left column comprises the abovementioned parameter(s) or conditions. The table comprises static valueswhich are set beforehand or preconfigured.

In some embodiments, the second network node 103 may be for example aMME node. The MME 103 is responsible for control signaling to and fromthe user equipments 101 within its geographical service area. Table 2below shows an example of a table for translation of messages andprocedures to normalized load for a MME node 103. Table 3 below shows anexample of a table for translation of messages and procedures tonormalized load where the second network node 103 is exemplified as anSGSN node 103. Note, the values, messages and procedures are onlyexamples. In principle all messages that initiate procedures thatconsume significant node processing resources would be comprised in thetranslation table.

TABLE 2 Examples of translation of messages and procedures to normalizedSignaling Load Values in the MME node 103 Parameter(s) or condition thatSignaling distinguish Load Ingress Message procedure Procedure ValuesAttach request Initial Attach 1 Detach request, UE-Initiated Detach,MME- 0.9 Detach notification, Initiated Detach, SGSN- Cancel Location,or Initiated Detach with ISR MME implicit detach activated, orHSS-Initiated event Detach Tracking Area Update Tracking Area Updatewith 0.2 Request or without S-GW change Context Request Tracking AreaUpdate (old 0.6 MME), RA Update with MME interaction with or withoutS-GW change Handover Required Intra-E-UTRAN S1-based 1.3 Handover(source MME), E-UTRAN to UTRAN Inter RAT Handover, or E-UTRAN to GERANInter RAT Handover, Forward Relocation Intra-E-UTRAN S1-based 1.3Request Handover (target MME), UTRAN to E-UTRAN Inter RAT Handover, orGERAN to E-UTRAN Inter RAT Handover PDN Connectivity UE Requested PDN0.5 Request Connectivity PDN Disconnection UE or MME Requested 0.4Request, or MME PDN Disconnection internal PDN disconnection triggerCreate Bearer Dedicated Bearer 0.3 Request Activation Update Bearer ForInsert Bearer Modification 0.2 Request, Insert Subscriber Data, ifSubscriber Data, or UE-AMBR or Request Bearer APN-AMBR is Resourcechanged Modification Delete Bearer Bearer Deactivation 0.2 Request, orMME internal Dedicated Bearer Deactivation Service Request, or UE orNetwork Triggered 0.2 Downlink Data Service Request Notification S1 UEContext S1 Release Procedures 0.1 Release Request

TABLE 3 Examples of translation of messages and procedures to normalizedSignaling Load Values in the SGSN node 103 Parameter(s) or conditionthat Signaling distinguish Load Ingress Message procedure ProcedureValues Attach request GPRS Attach, Combined 1   GPRS/IMSI Attach Detachrequest MS-Initiated Detach or 0.8 Network-Initiated Detach Routing AreaUpdate Old RAI is served Intra SGSN Routing Area 0.1 Request by thecurrent Update, Combined Intra node and the SGSN LA/RA update, or MS/UEis not Periodic RA (and LA) PMM-Connected Update Routing Area Update OldRAI is served Inter SGSN Routing Area 0.7 Request by a different Update,Combined Inter node and the SGSN LA/RA update MS/UE is not PMM-ConnectedRouting Area Update The MS/UE is in Inter-system Change 1.1 Request orSGSN PMM-Connected (Intra-SGSN or Inter- (Note 1) Context Request stateSGSN) Relocation Required Serving RNS Relocation 1.3 or ForwardProcedure, Combined (Note 1) Relocation Request Hard Handover and SRNSRelocation Procedure, and Combined Cell/URA Update and SRNS RelocationProcedure Enhanced Relocation Enhanced Serving RNS 0.3 Complete RequestRelocation PS Handover Target Cell Intra/Inter BSS and Intra 0.7Required Identifier is served SGSN PS Handover by the current ProcedureSGSN PS Handover For ‘PS Handover Inter SGSN and Inter RAT 0.8 Requiredor Forward Required’ only: PS Handover Procedure (Note 1) RelocationRequest Target Cell Identifier is served by a different SGSN ActivatePDP Context PDP Context Activation, 0.5 Request, Activate Secondary PDPContext Secondary PDP Activation, Network Context Request, or RequestPDP Context Initiate PDP Activation Activation Context RequestDeactivate PDP Deactivation procedures 0.4 Context Request, Delete PDPContext Request, or Delete Bearer Request Modify PDP ContextModification procedures 0.1 Request, Update PDP Context Request orUpdate Bearer Request Service Request MS, UE or Network 0.2 Initiatedservice Request RAB Release Release Procedures 0.1 Release Request, orIu Release Request Paging Request CS paging 0.1 (Note 1) Signaling LoadValues to be incremented in both target and source SGSN

The first network node 105 uses the table to find the signaling loadvalue that corresponds to or matches the detected received message andtriggered procedure. In some embodiments, the received message andtriggered procedure may fulfill conditions or parameters set in themessage, as shown in the middle left column of tables 1, 2 and 3 above.

Returning to FIG. 2.

Step 206

Each time the first network node 105 detects a message or receivesinformation about historical messages that matches one of the rows inthe translation table and optionally any specific parameter(s) orcondition(s), it increases a parameter called total signaling load valuefor the second network node 103 with the value found in the rightmostcolumn of tables 1, 2 and 3. The total signaling load value may bereferred to as the first total signaling load value.

In the example of table 1, the total signaling load value is:

Total Signaling LoadValue=SLV(message_(—)1)+SLV(message_(—)2)+SLV(message3)+SLV(message_(—)4)+SLV(message_(—)5)=1+0.8+0.2+1.5+0.1+0.7=4.3

In order to get an instantaneous signaling load value, the totalsignaling load value is read periodically, e.g. once per second, by asoftware function, method or script in the first network node 105, andthe difference between the new and the previous value is divided by theelapsed time. The software function is illustrated in FIGS. 3 and 4. Thetotal signaling load value for a time interval may be referred to as thesecond total signaling load value or a total signaling load value rateper time interval:

${{SecondTotalSignalingLoadValue}\mspace{14mu} = \frac{\begin{matrix}{{{SignalingLoadValue}\mspace{20mu} \left( {t\; 2} \right)} -} \\{{SignalingLoadValue}\mspace{20mu} \left( {t\; 1} \right)}\end{matrix}}{{t\; 2} - {t\; 1}}},$

where t1 is the time when the previous value is measured and t2 is thetime when the new value is measured.

In some embodiments, the first network node 105 measures and/or monitorsthe number of signaling load value per user equipment 101. When thesignaling load value is measured per user equipment 101, the measurementmay be presented for a different time period than for the second networknode total e.g. the signaling load per day for the user equipment 101instead of signaling load per second for the second network node 103 intotal. The measurement may be done completely within the first networknode 105, outside the first network node 105, e.g. based on eventnotifications, or a combination of the both. In some embodiments, it maybe created in real time or as post processing from collected statistics.

The per user equipment signaling load value rate, may be for one,several or all user equipments 101 in the network 100. The userequipments 101 may be grouped into different categories depending onwhat signaling load they generate in the second network node 103/network100. For example, different categories may be user equipments 101generating 0-1.9 SLV/day, 2.0-5.9 SLV/day, 6.0-20 SLV/day or 21 or moreSLV/day. Understanding what categories of user equipments 101 there arein a second network node 103 or network 100 may make network planningeasier. For example, if and how much network capacity needs to beexpanded if a contract of 10 million M2M devices of category 0-1.9SLV/day is being negotiated.

Other parameters than signaling load value may be used in creating thecategories, e.g. the amount of mobility signaling, e.g. to differentiatestationary devices, time of day when active, e.g. service requestsduring peak load hours or during low peak hours etc. These parametersmay be extracted from the event information, e.g. messages/signals, thatare the base for the SLV calculation method.

The total signaling load value may also be calculated per procedureexecuted in the second network node 103.

Step 207

The first network node 105 may determine or calculate a maximumsignaling load value capacity of the second network node 103 if thenumber of received messages is increased until a maximum processingpower capacity of the second network node 103 is reached, e.g. the CPUof the second network node 103 are at max capacity or any other suitablecriteria. The maximum signaling load value capacity is a measure of howmuch signaling load values the second network node 103 is able to handleper time interval, e.g. second, i.e. based on its amount of availableprocessing power.

Step 208

The first network node 105 measures processing power in the secondnetwork node 103 based on the signaling load value. The measurement maybe of processing power usage in the second network node 103. It may bebased on one signaling load value, the different alternatives of totalsignaling load value, the maximum signaling load value capacity etc. Ifthe signaling load value comes close to, reaches or passes an upperlimit, the second network node 103 capacity, i.e. processing power,needs to be increased e.g. to deploy more of the resource that ismissing.

Step 209

The first network node 105 determines or calculates a resource valuebased on the measured processing power. It may also be associated withthe determined maximum signaling load value capacity of the secondnetwork node 103. The resource value may further be based on thedifferent types total signaling load value described in step 206.

Step 210

The first network node 105 sends or communicates information about thesignaling load value and the total signaling load value, both per secondnetwork node 103, per user equipment 101, per procedure and per timeinterval, or a combination of these, the processing power and theprocessing power usage to the third network node 107. The third networknode 107 may be a monitoring node such as an OSS or other O&M nodelocated at the operator. The information may in addition be communicatedto the vendor of the second network node 103 for statistical and/orlicensing purposes.

Based on the separation of memory resources and processing resources, aformula for a flexible dimensioning model may be expressed. In someembodiments, a flexible price/license model may also be expressed.

The existing measures, i.e. registered users (SAU) and number ofconnections, are kept but tied more to the memory resource utilizationin the second network node 103.

Step 211

The third network node 107 monitors, processes and presents the receivedinformation about the measurements of processing power and processingpower usage from the first network node 105. The measurements may beunified measurements in case a plurality of messages of different typesis received. The total number of signaling load values in a secondnetwork node 103 may be measured and monitored at any given moment andstatistics collected. The owner and/or the vendor of the second networknode 103 may use the measurements/statistics to verify that thesignaling load value measured doesn't pass its upper limit. If thesignaling load value passes its upper limit, the second network node 103capacity, i.e. processing power, may need to be increased e.g. to deploymore of the resource that is missing. By this, a tool for fairpricing/licensing that may be flexible to also accommodate the wildlydifferent communication patters for many M2M applications may beobtained.

When the first network node 105 is integrated in the second network node103, illustrated as alternative 1 in FIG. 1, the third network node 107may receive its input data directly from the first network node 103.This is also illustrated in FIG. 3.

When the first network node is integrated din the third network node107, illustrated as alternative 2 in FIG. 1, the second network node 103creates, as mentioned above, an event log of messages and signaling loadvalue events. This log is provided to the first network node 105, whichmay also be referred to as a post processing node. The first networknode 105 stores the received signaling load value events and performspost processing of the stored data. This is also illustrated in FIG. 4.The post processing may for example be beneficial when data from severalor all nodes in the network 100 shall be monitored and presented or whenthe categorization needs to be more advanced e.g. comprising otherparameters than signaling load value, e.g. mobility signaling, activetime-of-day etc.

In some embodiments, the price for a second network node 103 may becalculated using a model where the Signaling Load Value (SLV) affectsthe price independently from the Simultaneously Attached Users (SAU) forexample using a base formula as this. PDP Context/PDN Connections mayreplace SAU e.g. for GGSN/PGW.

Node Price=x*SAU+y*SLV/s+z*PPS

-   -   x may e.g. be measured in SEK/SAU    -   y may e.g. be measured in SEK/SLV/s    -   z may e.g. be measured in SEK/PPS

In a simplified example to illustrate the price model, using a secondnetwork node 103 exemplified as an MME, the prices of two different MMEnodes 103 are calculated. One MME 103 dimensioned for normal and smartphone usage, referred to as MME_(—)1, and a second MME 103 dimensionedfor a dominant portion of low activity M2M devices, referred to asMME_(—)2.

The following prices are used in the example: x=0.1 SEK/SAU, y=900SEK/SLV/s, z=0.01 SEK/PPS. The following illustrative assumptions aremade on the node dimensioning. Note that the values in these examplesand assumptions are only explanatory and are not necessarily used inreal products or deployments:

-   -   MME_(—)1 103 is dimensioned for 1 M SAU, and MME_(—)2 103 is        dimensioned for 10 M SAU;    -   deduced from traffic models it is assumed that an attached        normal/smart phone users need 0.001 SLV/s;    -   low activity M2M devices are optimized and generate less than        one tenth of the signaling load of normal/smart phone users,        i.e. 0.0001 SLV/s;    -   An MME 103 does not have any packet forwarding capacity;

The price for a “normal” MME_(—)1 103 of 1 M SAU would then be:

Node Price MME_(—)1=0.1*10E6+900*10E6*10E-3+0.01*0=1 MSEK

The price for “M2M tailored” MME_(—)2 of 10 M SAU would then be:

Node Price MME_(—)2=0.1*10E7+900*10E7*10E-4+0.01*0=1.9 MSEK

Note that an operator that buys an M2M tailored MME 103 of 10 M SAU asin the example above and uses it for solely normal/smart phone users,would still only be able to serve approximately 1 M SAU due to thelimiting signaling capacity, i.e. SLV/s.

One particular use of the price model is a when the node price is solelybased on SLV/s, i.e. x and z above are set to 0.

The method described above will now be described seen from theperspective of the first network node 105. FIG. 5 is a flowchartdescribing the present method in the first network node 105 formeasuring processing power in a second network node 103 in thecommunications network 100. In some embodiments, the measurement ofprocessing power is a unified measurement valid for different types ofmessages. Unified refers to making or uniting something into one unit ora coherent whole. In some embodiments, the second network node 103 is aMobility Management Entity, referred to as MME, a Serving General PacketRadio Service Support Node, referred to as SGSN, a Gateway GeneralPacket Radio Service Support Node, referred to as GGSN, a ServingGateway, referred to as S-GW, a Packet Data Network Gateway, referred toas P-GW, a Machine Type Communication Interworking Function node,referred to as MTC IWF and the third network node 107 is a monitoringnode 107. In some embodiments, the fourth network node 101 is a userequipment 101 or a fourth network node configured to communicate withthe second network node 103. The method comprises the steps to beperformed by the first network node 105:

Step 501

This step corresponds to step 202 and 204 a in FIG. 2.

In some embodiments, the first network node 105 is comprised in thesecond network node 103. In some embodiments, the first network node 105detects receipt of a message from a fourth network node 101. The messagemay be of different types.

In some embodiments, the received message fulfils a predeterminedcondition.

Step 502

This step corresponds to step 203 in FIG. 2. This is a step which isperformed after step 501.

In some embodiments, the first network node 105 is comprised in thesecond network node 103. In some embodiments, the first network node 105executes the procedure triggered by the received message.

In some embodiments, the procedure executed in the second network node103 is decided by the received message together with one or morepredetermined conditions and/or one or more parameters in the message.

Step 503

This step corresponds to step 204 b in FIG. 2. This step is performedinstead of steps 501 and 502.

In some embodiments, the first network node 105 is comprised in a thirdnetwork node 107. In some embodiments, the first network node 105receives information about the message from the second network node 103.The message is sent from a fourth network node 101 to the second networknode 103.

Step 504

This step corresponds to step 205 in FIG. 2.

The first network node 105 obtains a signaling load value associatedwith a procedure. The procedure is triggered by a message.

In some embodiments, the signaling load value associated with theprocedure is preconfigured in the first network node 105.

In some embodiments, the signaling load value is further associated withconsumption of an amount of processing power/resources when theprocedure is executed in the second network node 103.

In some embodiments, the signaling load value, information about themessage, conditions and parameters associated with the procedure, andinformation about the signaling load value associated with the procedureis stored in a table in the first network node 105. In some embodiments,the signaling load value is obtained from the table.

Step 505

This step corresponds to step 206 in FIG. 2. In some embodiments, thefirst network node 105 adds the obtained signaling load value to a firsttotal signaling load value.

In some embodiments, the first total signaling load value is per fourthnetwork node 101, per procedure executed in the second network node 103,per time interval or any combination of these.

Step 506

This step corresponds to step 207 in FIG. 2.

In some embodiments, the first network node 105 determines a maximumcapacity of signaling load value of the second network node 103 byincreasing a number of received messages until a maximum capacity ofprocessing power of the second network node 103 is reached. The maximumcapacity of signaling load value may also be referred to as maximumsignaling load value capacity.

Step 507

This step corresponds to step 209 in FIG. 2.

In some embodiments, the first network node 105 determines a resourcevalue associated with the determined maximum capacity of signaling loadvalue of the second network node 103.

Step 508

This step corresponds to step 206 in FIG. 2.

In some embodiments, the first network node 105 determines a secondtotal signaling load value per fourth network node 101 and per timeperiod.

Step 509

This step corresponds to step 206 in FIG. 2. This step is performedafter step 508.

In some embodiments, the first network node 105 establishes a categoryof fourth network node 101 based on the second total signaling loadvalue. The category of fourth network node 101 and the understanding ofthe number of fourth network nodes 101 of different categories in anetwork facilitate and/or enables network planning and dimensioning ofthe communications network 100.

Step 510

This step corresponds to step 210 in FIG. 2.

In some embodiments, the first network node 105 sends information aboutthe first total signaling value and the second total signaling loadvalue to a third network node 107.

Step 511

This step corresponds to step 208 in FIG. 2.

The first network node 105 measures the processing power of the secondnetwork node 103 based on the obtained signaling load value.

In some embodiments, the measurement of the processing power in thesecond network node 103 is further based on the total signaling loadvalue. As mentioned above, the message may be of different types. Themeasurement of processing power based on the total signaling load valuesmay therefore be a unified measurement of processing power. Unifiedindicates that the measurement of processing power is independent of thedifferent types of messages, and that it is one measurement of all typesof messages.

In some embodiments, the measurement of the processing power of thesecond network node 103 is further based on the determined maximumcapacity of signaling load value.

To perform the method steps shown in FIG. 5 for measuring processingpower in a second network node 103 in a communications network 100, thefirst network node 105 comprises a first network node arrangement asshown in FIG. 6. In some embodiments, the second network node 103 is aMobility Management Entity, referred to as MME, a Serving General PacketRadio Service Support Node, referred to as SGSN, a Gateway GeneralPacket Radio Service Support Node, referred to as GGSN, a ServingGateway, referred to as S-GW, a Packet Data Network Gateway, referred toas P-GW, a Machine Type Communication Interworking Function node,referred to as MTC IWF and the third network node 107 is a monitoringnode 107. In some embodiments, the fourth network node 101 is a userequipment 101 or a fourth network node configured to communicate withthe second network node 103.

The first network node 105 comprises an obtaining unit 601 configured toobtain a signaling load value associated with a procedure. The procedureis triggered by a message. In some embodiments, the signaling load valueassociated with the procedure is preconfigured in the first network node105. In some embodiments, the signaling load value is further associatedwith consumption of an amount of processing power/resources when theprocedure is executed in the second network node 103. In someembodiments, signaling load value, information about the message,conditions and parameters associated with the procedure and informationabout the signaling load value associated with the procedure is storedin a table in the first network node 105. In some embodiments, thesignaling load value is obtained from the table.

The first network node 105 further comprises a measuring unit 603 whichis configured to measure of the processing power of the second networknode 103 in the communications network 100 based on the obtainedsignaling load value. In some embodiments, the measuring unit 603 isfurther configured to measure the processing power in the second networknode 103 further based on the first total signaling load value. In someembodiments, the measuring unit 603 is further configured to measure theprocessing power of the second network node 103 further based on thedetermined maximum capacity of signaling load value.

In some embodiments, where the first network node 105 is comprised inthe second network node 103, the first network node 105 comprises adetecting unit 605 configured to detect receipt of a message from afourth network node 101, and a processing unit 607 configured to executethe procedure triggered by the message. In some embodiments, theprocedure executed in the second network node 103 is decided by areceived message together with one or more predetermined conditionsand/or one or more parameters in the message. In some embodiments, theprocessing unit 607 is further configured to add the obtained signalingload value to a first total signaling load value. In some embodiments,the total signaling load value is per fourth network node 101, perprocedure executed in the second network node 103, per time interval, ora combination of these. In some embodiments, the processing unit 607 isfurther configured to determine a maximum signaling load value capacityof the second network node 103 by increasing a number of receivedmessages until a maximum capacity of processing power of the secondnetwork node 103 is reached. In some embodiments, the processing unit607 is further configured to determine a resource value associated withthe determined maximum capacity of signaling load value of the secondnetwork node 103. In some embodiments, the processing unit 607 isfurther configured to determine a second total signaling load value perfourth network node 101 and per time period and to establish a categoryof fourth network node 101 based on the second total signaling loadvalue. In some embodiments, the category of fourth network node 101enables network planning and dimensioning of the communications network100.

In some embodiments, where the first network node 105 is comprised in athird network node 107, the first network node 105 comprises a receivingunit 610 configured to receive information about the message from thesecond network node 103. The message is sent from a fourth network node101 to the second network node 103. In some embodiments, the receivedmessage fulfils a predetermined condition

In some embodiments, the first network node 105 further comprises asending unit 612 configured to send information about the first totalsignaling value and the second total signaling load value to a thirdnetwork node 107.

The present mechanism for measuring processing power in a second networknode 103 in a communications network 100 may be implemented through oneor more processors, such as the processing unit 607 in the first networknode arrangement depicted in FIG. 6, together with computer program codefor performing the functions of the embodiments herein. The processormay be for example a Digital Signal Processor (DSP), ApplicationSpecific Integrated Circuit (ASIC) processor, Field-programmable gatearray (FPGA) processor or micro processor. The program code mentionedabove may also be provided as a computer program product, for instancein the form of a data carrier carrying computer program code forperforming the embodiments herein when being loaded into the firstnetwork node 105. One such carrier may be in the form of a CD ROM disc.It is however feasible with other data carriers such as a memory stick.The computer program code may furthermore be provided as pure programcode on a server and downloaded to the first network node 105 remotely.

The embodiments herein are not limited to the above described preferredembodiments. Various alternatives, modifications and equivalents may beused. Therefore, the above embodiments should not be taken as limitingthe scope of the embodiments, which is defined by the appending claims.

It should be emphasized that the term “comprises/comprising” when usedin this specification is taken to specify the presence of statedfeatures, integers, steps or components, but does not preclude thepresence or addition of one or more other features, integers, steps,components or groups thereof. It should also be noted that the words “a”or “an” preceding an element do not exclude the presence of a pluralityof such elements.

It should also be emphasized that the steps of the methods defined inthe appended claims may, without departing from the embodiments herein,be performed in another order than the order in which they appear in theclaims.

1. A method in a first network node (105) for measuring processing powerin a second network node (103) in a communications network (100), themethod comprising: obtaining (205, 504) a signaling load valueassociated with a procedure, which procedure is triggered by a message;and measuring (208, 511) the processing power of the second network node(103) based on the obtained signaling load value.
 2. The methodaccording to claim 1, wherein the first network node (105) is comprisedin the second network node (103), and wherein the method furthercomprises: detecting (202, 204 a, 501) receipt of the message from afourth network node (101); and executing (203, 502) the proceduretriggered by the received message.
 3. The method according to claim 1,wherein the first network node (105) is comprised in a third networknode (107), and wherein the method further comprises: receiving (204 b,503) information about the message from the second network node (103);and which message is sent from a fourth network node (101) to the secondnetwork node (107).
 4. The method according to any of the claims 1-3,further comprising: adding (206, 505) the obtained signaling load valueto a first total signaling load value; and wherein the measuring (208,511) the processing power in the second network node (103) is furtherbased on the total signaling load value.
 5. The method according toclaim 4, wherein the first total signaling load value is at least one ofper fourth network node (101), per procedure executed in the secondnetwork node (103) and per time interval.
 6. The method according to anyof the claims 1-5, further comprising: determining (207, 506) a maximumcapacity of signaling load value of the second network node (103) byincreasing a number of received messages until a maximum capacity ofprocessing power of the second network node (103) is reached; andwherein the measuring (208, 511) the processing power of the secondnetwork node (103) is further based on the determined maximum capacityof signaling load value.
 7. The method according to claim 6, furthercomprising: determining (209, 507) a resource value associated with thedetermined maximum capacity of signaling load value of the secondnetwork node (103).
 8. The method according to any of the claims 1-7,further comprising: determining (206, 508) a second total signaling loadvalue per fourth network node (101) and per time period; andestablishing (206, 509) a category of fourth network node (101) based onthe second total signaling load value; and wherein the category offourth network node (101) enables network planning and dimensioning ofthe communications network (100).
 9. The method according to any of theclaims 1-8, further comprising: sending (210, 510) information about thefirst total signaling value and the second total signaling load value toa third network node (107).
 10. The method according to any of theclaims 1-9, wherein the signaling load value associated with theprocedure is preconfigured in the first network node (105).
 11. Themethod according to any of the claims 1-10, wherein the received messagefulfils a predetermined condition.
 12. The method according to any ofthe claims 1-11, wherein the signaling load value is further associatedwith consumption of an amount of processing power when the procedure isexecuted in the second network node (103).
 13. The method according toany of the claims 1-12, wherein information about the message,conditions and parameters associated with the procedure and informationabout the signaling load value associated with the procedure is storedin a table in the first network node (105), and wherein the signalingload value is obtained from the table.
 14. The method according to anyof the claims 1-13, wherein the second network node (103) is a MobilityManagement Entity, referred to as MME, a Serving General Packet RadioService Support Node, referred to as SGSN, a Gateway General PacketRadio Service Support Node, referred to as GGSN, a Serving Gateway,referred to as S-GW, a Packet Data Network Gateway, referred to as P-GW,a Machine Type Communication Interworking Function node, referred to asMTC IWF, wherein the third network node (107) is a monitoring node (107)and wherein the fourth network node (101) is a user equipment (101) or afourth network node configured to communicate with the second networknode (103).
 15. A first network node (105) for measuring processingpower in a second network node (103) in a communications network (100),the first network node (105) comprising: an obtaining unit (601)configured to obtain a signaling load value associated with a procedure,which procedure is triggered by a message; and a measuring unit (603)configured to measure the processing power of the second network node(103) in the communications network (100) based on the obtainedsignaling load value.
 16. The first network node (105) according toclaim 15, wherein the first network node (105) is comprised in thesecond network node (103), and wherein the first network node (105)further comprises: a detecting unit (605) configured to detect receiptof the message from a fourth network node (101); and a processing unit(607) configured to execute the procedure triggered by the message. 17.The first network node (105) according to claim 15, wherein the firstnetwork node (105) is comprised in a third network node (107), andwherein the first network node (105) further comprises: a receiving unit(610) configured to receive information about the message from thesecond network node (103); and which message is sent from a fourthnetwork node (101) to the second network node (103).
 18. The firstnetwork node (105) according to any of the claims 15-17, wherein theprocessing unit (607) is further configured to add the obtainedsignaling load value to a first total signaling load value; and whereinthe measuring unit (603) is further configured to measure the processingpower in the second network node (103) further based on the totalsignaling load value.
 19. The first network node (105) according toclaim 18, wherein the first total signaling load value is at least oneof per fourth network node (101), per procedure executed in the secondnetwork node (103) and per time interval.
 20. The first network node(105) according to any of the claims 15-19, wherein the processing unit(607) is further configured to determine a maximum capacity of signalingload value of the second network node (103) by increasing a number ofreceived messages until a maximum capacity of processing power of thesecond network node (103) is reached; and wherein the measuring unit(603) is further configured to measure the processing power of thesecond network node (103) further based on the determined maximumcapacity of signaling load value.
 21. The first network node (105)according to claim 20, wherein the processing unit (607) is furtherconfigured to determine a resource value associated with the determinedmaximum capacity of signaling load value of the second network node(103).
 22. The first network node (105) according to any of the claims15-21, wherein the processing unit (607) is further configured to:determine a second total signaling load value per fourth network node(101) and per time period; and to establish a category of fourth networknode (101) based on the second total signaling load value; and whereinthe category of fourth network node (101) enables network planning anddimensioning of the communications network (100).
 23. The first networknode (105) according to any of the claims 15-22, further comprising: asending unit (612) configured to send information about the first totalsignaling value and the second total signaling load value to a thirdnetwork node (107).
 24. The first network node (105) according to any ofthe claims 15-23, wherein the signaling load value associated with theprocedure is preconfigured in the first network node (105).
 25. Thefirst network node (105) according to any of the claims 15-24, whereinthe received message fulfils a predetermined condition.
 26. The firstnetwork node (105) according to any of the claims 15-25, wherein thesignaling load value is further associated with consumption of an amountof processing power when the procedure is executed in the second networknode (103).
 27. The first network node (105) according to any of theclaims 15-26, wherein information about the message, conditions andparameters associated with the procedure and information about thesignaling load value associated with the procedure is stored in a tablein the first network node (105), and wherein the obtaining unit (601) isfurther configured to obtain the signaling load value from the table.28. The first network node (105) according to any of the claims 15-27,wherein the second network node (103) is a Mobility Management Entity,referred to as MME, a Serving General Packet Radio Service Support Node,referred to as SGSN, a Gateway General Packet Radio Service SupportNode, referred to as GGSN, a Serving Gateway, referred to as S-GW, aPacket Data Network Gateway, referred to as P-GW, a Machine TypeCommunication Interworking Function node, referred to as MTC IWF,wherein the third network node (107) is a monitoring node (107), andwherein the fourth network node (101) is a user equipment (101) or afourth network node configured to communicate with the second networknode (103).